chore(blog): add october summary #3362
Conversation
thulieblack
requested review from
quetzalliwrites,
derberg,
akshatnema,
magicmatatjahu,
anshgoyalevil,
Mayaleeeee and
asyncapi-bot-eve
as code owners
WalkthroughThe changes include the creation of a new community update document for October 2024, summarizing the AsyncAPI Conference and outlining future community goals. Additionally, existing documents have been expanded with detailed accounts of past events and updates on community initiatives. Notable enhancements include the migration of Glee to a monorepo structure and the introduction of a new package, Gleequore. The updates aim to improve community engagement and participation in upcoming events and initiatives. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
asyncapi-bot
requested review from
devilkiller-ag,
sambhavgupta0705,
BhaswatiRoy,
J0SAL,
TRohit20 and
VaishnaviNandakumar
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3362 +/- ##
=======================================
Coverage 49.14% 49.14%
=======================================
Files 21 21
Lines 647 647
=======================================
Hits 318 318
Misses 329 329 ☔ View full report in Codecov by Sentry. |
thulieblack
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Outside diff range and nitpick comments (1)
markdown/blog/2024-october-summary.md (1)
17-20: Minor grammatical improvement suggested.Consider restructuring the first sentence for better flow.
-October marked the third AsyncAPI Conference, this time an online edition. As someone fortunate enough to be extensively involved in organizing the conferences, I saw the challenges that came with in-person events. +October marked the third AsyncAPI Conference with an online edition. As someone fortunate enough to be extensively involved in organizing the conferences, I witnessed the challenges that came with in-person events.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (4)
markdown/blog/2024-october-summary.md(1 hunks)markdown/blog/2024-september-summary-and-london.md(0 hunks)markdown/blog/asyncapi-bounty-program-2024.md(0 hunks)markdown/blog/helsinki-and-community.md(0 hunks)
💤 Files with no reviewable changes (3)
- markdown/blog/2024-september-summary-and-london.md
- markdown/blog/asyncapi-bounty-program-2024.md
- markdown/blog/helsinki-and-community.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-october-summary.md
[style] ~31-~31: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...on December 5th in Paris, thanks to the amazing team at APIdays. [The draft agenda is n...
(AWESOME)
[duplication] ~53-~53: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (2)
markdown/blog/2024-october-summary.md (2)
1-15: LGTM! Frontmatter is well-structured.
All required metadata fields are present and properly formatted.
131-132: LGTM! Clear and informative upcoming section.
The newsletter information is well-presented with a clear call-to-action.
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-3362--asyncapi-website.netlify.app/ |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
markdown/blog/2024-october-summary.md (2)
21-22: Remove extra blank line.There's an unnecessary double blank line after the introduction paragraph.
I want to express my gratitude to our financial sponsors, [Gravitee.io](https://www.gravitee.io/) and [Postman](https://www.postman.com/), as well as to the speakers for their engaging talks and the conference volunteers (*be sure to check out the Hall of Fame section*). [I encourage you to watch the recorded sessions if you missed the event](https://www.youtube.com/watch?v=XGn8v0yBfOI&t=1895s). A playlist of the talks and their slides will also be available on the [conference website](https://conference.asyncapi.com/). -
53-130: Improve name formatting consistency.Consider standardizing the name formats across profiles. Some entries use full names while others use single names:
- 'Oluwabamikemi' vs 'Victoria Nduka'
- 'Miracle' vs 'Ashmit Jagtap'
- 'Olumide' vs 'Fuad ALIPHATIC Adegoke'
🧰 Tools
🪛 LanguageTool
[duplication] ~53-~53: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...(ENGLISH_WORD_REPEAT_RULE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-october-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-october-summary.md
[style] ~31-~31: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...on December 5th in Paris, thanks to the amazing team at APIdays. [The draft agenda is n...
(AWESOME)
[duplication] ~53-~53: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (5)
markdown/blog/2024-october-summary.md (5)
1-15: LGTM! Frontmatter is well-structured.
All required metadata fields are present and properly formatted.
23-26: LGTM! Clear and informative section.
The community goals section effectively communicates the 2025 objectives and encourages community participation.
40-41: Empty section needs attention.
The "AsyncAPI Conference Rebranding" section is still empty. Either add content or remove this section.
42-48: LGTM! Clear technical update.
The section effectively communicates the technical changes to Glee and provides proper references.
132-133: LGTM! Clear upcoming event information.
The section effectively communicates the upcoming newsletter and provides subscription information.
|
@derberg please review |
|
@thulieblack Any action items in the nitpick changes? 
|
There was a problem hiding this comment.
I think it would make sense to mention mascot rebranding work, even show pictures of latest proposal to get people involved
maybe would be good to mention FOSDEM CFP? https://www.linkedin.com/feed/update/urn:li:activity:7259155690206707712/
not official AsyncAPI event but kinda community related
please also include asyncapi/community#1577
| October marked the third AsyncAPI Conference, this time an online edition. As someone fortunate enough to be extensively involved in organizing the conferences, I saw the challenges that came with in-person events. | ||
| It gave me the idea to propose bringing back the online edition as part of the AsyncAPI Conference brand. We're glad and excited that we received positive results, with over **330 views** from attendees who watched and engaged with us. | ||
|
|
||
| I want to express my gratitude to our financial sponsors, [Gravitee.io](https://www.gravitee.io/) and [Postman](https://www.postman.com/), as well as to the speakers for their engaging talks and the conference volunteers (*be sure to check out the Hall of Fame section*). [I encourage you to watch the recorded sessions if you missed the event](https://www.youtube.com/watch?v=XGn8v0yBfOI&t=1895s). A playlist of the talks and their slides will also be available on the [conference website](https://conference.asyncapi.com/). |
There was a problem hiding this comment.
will the talks be also shared as individual videos? we did it for pervious editions, and it was good source for social media content
There was a problem hiding this comment.
Yes, we'll embed the playlist on the conference website and share it on socials. @iambami is currenlty in the process of trimming the videos
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (4)
markdown/blog/2024-october-summary.md (4)
17-18: Consider clarifying the attendance metric.Using "360 views" might not accurately represent unique attendee participation. Consider specifying if this number represents unique attendees, peak concurrent viewers, or total views.
-We're glad and excited that we received positive results, with over **360 views** from attendees who watched and engaged with us. +We're glad and excited that we received positive results, with over **360 unique viewers** who watched and engaged with us.
44-48: Add FOSDEM dates and more context.Consider adding the event dates and location to help readers plan their attendance. Also, mention the submission deadline for the Call for Participation.
### AsyncAPI at FOSDEM 2025 -Are you attending FOSDEM and interested in speaking? AsyncAPI will participate in the FOSDEM conference as part of the `APIs: GraphQL, OpenAPI, AsyncAPI, and Friends` track. +Are you attending FOSDEM 2025 (February 3-4, 2025 in Brussels, Belgium) and interested in speaking? AsyncAPI will participate in the conference as part of the `APIs: GraphQL, OpenAPI, AsyncAPI, and Friends` track. [The Call for Participation is now open](https://pretalx.fosdem.org/fosdem-2025/cfp), and we encourage everyone in the community to apply. This is another great opportunity to meet fellow community members! + +The deadline for talk submissions is December 15, 2024.
49-55: Consider adding technical details about the changes.To help developers understand the impact, consider adding:
- Links to migration guides or documentation
- Examples of how to use Gleequore
- List of supported protocols for browser integration
71-148: Fix Profiles component usage.The component shows word duplication in its props.
-<Profiles profiles={[ +<Profiles items={[🧰 Tools
🪛 LanguageTool
[duplication] ~71-~71: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...(ENGLISH_WORD_REPEAT_RULE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-october-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-october-summary.md
[style] ~31-~31: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...on December 5th in Paris, thanks to the amazing team at APIdays. [The draft agenda is n...
(AWESOME)
[style] ~58-~58: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... Eve and Chan mascots. The designs look amazing so far! <Figure src="/img/posts/2024...
(AWESOME)
[duplication] ~71-~71: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (4)
markdown/blog/2024-october-summary.md (4)
1-15: LGTM!
The front matter is well-structured and contains all required metadata fields.
23-26: LGTM!
Clear explanation of the 2025 goals proposal with appropriate call-to-action for community participation.
56-67: LGTM!
Well-structured section with appropriate visual content and clear call-to-action for community feedback.
🧰 Tools
🪛 LanguageTool
[style] ~58-~58: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... Eve and Chan mascots. The designs look amazing so far! <Figure src="/img/posts/2024...
(AWESOME)
150-151: LGTM!
Concise section with clear call-to-action for newsletter subscription.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
markdown/blog/2024-october-summary.md (3)
17-20: Consider formatting the view count consistently.The content is well-structured, but for consistency in technical writing, consider using numerals for the view count.
-with over **360 views** +with over **360+ views**
46-47: Consider adding the track's full details.For better visibility and searchability, consider including the full track name and any relevant track identifiers or links.
-as part of the `APIs: GraphQL, OpenAPI, AsyncAPI, and Friends` track. +as part of the ["APIs: GraphQL, OpenAPI, AsyncAPI, and Friends" devroom](https://fosdem.org/2025/schedule/track/apis/).
52-58: Consider adding specific package details.While the section explains the changes well, consider adding:
- Direct links to the Gleequore package
- Brief example of how to use the new package
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-october-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-october-summary.md
[style] ~31-~31: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...on December 5th in Paris, thanks to the amazing team at APIdays. [The draft agenda is n...
(AWESOME)
[style] ~61-~61: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... Eve and Chan mascots. The designs look amazing so far! <Figure src="/img/posts/2024...
(AWESOME)
[duplication] ~74-~74: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (6)
markdown/blog/2024-october-summary.md (6)
1-15: LGTM! Frontmatter is well-structured.
The metadata is complete and follows the correct format.
23-26: LGTM! Clear presentation of community goals.
The section effectively communicates the purpose and provides a clear call to action with the PR reference.
49-50: LGTM! Clear presentation of the UN Global Digital Compact initiative.
The section effectively explains the context and provides a clear call to action.
59-70: LGTM! Well-structured mascot update section.
The section effectively presents the mascot updates with proper image formatting and reference links.
🧰 Tools
🪛 LanguageTool
[style] ~61-~61: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... Eve and Chan mascots. The designs look amazing so far! <Figure src="/img/posts/2024...
(AWESOME)
71-151: LGTM! Well-structured volunteer recognition section.
The Profiles component is used effectively to showcase the volunteers with consistent formatting.
🧰 Tools
🪛 LanguageTool
[duplication] ~74-~74: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
153-154: LGTM! Clear presentation of upcoming content.
The section effectively promotes the newsletter with a clear call to action.
|
@derberg another review please |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (5)
markdown/blog/2024-october-summary.md (5)
17-20: Consider adding more engagement metrics.While the "360 views" metric is good, consider including additional engagement metrics such as:
- Average watch time
- Peak concurrent viewers
- Number of questions asked
- Geographic distribution of attendees
31-31: Consider using more formal language.Replace "amazing team" with a more professional alternative such as "exceptional team" or "outstanding team".
🧰 Tools
🪛 LanguageTool
[style] ~31-~31: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...on December 5th in Paris, thanks to the amazing team at APIdays. [The draft agenda is n...(AWESOME)
53-58: Consider adding more technical details about the migration.To help developers better understand the changes, consider adding:
- Key differences between the old and new structure
- Migration guide for existing users
- Examples of how to use Gleequore
62-62: Consider using more formal language.Replace "amazing" with a more professional alternative such as "impressive" or "exceptional".
🧰 Tools
🪛 LanguageTool
[style] ~62-~62: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... Eve and Chan mascots. The designs look amazing so far! <Figure src="/img/posts/2024...(AWESOME)
154-155: Consider adding newsletter preview content.To increase subscription interest, consider adding:
- Key topics to be covered
- Featured community members
- Any special announcements
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
markdown/blog/2024-october-summary.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-october-summary.md
[style] ~31-~31: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...on December 5th in Paris, thanks to the amazing team at APIdays. [The draft agenda is n...
(AWESOME)
[style] ~62-~62: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ... Eve and Chan mascots. The designs look amazing so far! <Figure src="/img/posts/2024...
(AWESOME)
[duplication] ~75-~75: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (4)
markdown/blog/2024-october-summary.md (4)
1-15: LGTM! Frontmatter is well-structured.
All required metadata fields are present and properly formatted.
23-26: LGTM! Clear communication of community goals.
The section effectively outlines the goals and provides a clear path for community engagement through the PR discussion.
49-51: LGTM! Clear explanation of the UN Digital Compact initiative.
The section effectively explains the initiative's relevance to AsyncAPI and provides a clear path for community participation.
75-152: LGTM! Well-structured volunteer recognition section.
The Profiles component effectively showcases the volunteers' contributions.
🧰 Tools
🪛 LanguageTool
[duplication] ~75-~75: Possible typo: you repeated a word
Context: ... and execution of the event seamless. <Profiles profiles={[ { name: 'Victoria Nduka', ...
(ENGLISH_WORD_REPEAT_RULE)
|
/rtm |
|
/rtm |
octobersummary + conference update
Summary by CodeRabbit
Release Notes
New Features
Enhancements
Bug Fixes